Blog

Importance of Var Scoping

Luis Majano September 24, 2010

Spread the word

Luis Majano

September 24, 2010

Spread the word


Share your thoughts

I can honestly say that there are always requests on the ColdBox lists or work that say, "Hey the application is taking my server memory, why does ColdBox do that!".  First of all, the ColdBox platform when placed in memory is less than 1kb of memory.  The rest that gets loaded into an application is because of your application code.  Second, the biggest culprit is the misuse or the not using of var scoped variables in event handlers or domain objects.

This is KEY!  Event handlers in ColdBox are cached by default so no unnecessary object creations occur.  Therefore, your code within the event handler functions MUST be thread safe and var scoped.  This is essential and key for ANY framework or ANY ColdFusion Component declaration, ALWAYS ALWAYS var scope.  I cannot stress the importance of having to var scope your ColdFusion component method calls.  I see this time and time again and we need to educated ourselves about it and also create a habit of ALWAYS var scoping our variables within function declarations.  What do you think?

Add Your Comment

(3)

Sep 30, 2010 10:28:54 UTC

by Allen

Not to be trite but the var keyword is a keyword, not a scope. Most of know that but I'd hate to see a newbie get confused.

Do you have some example code for a handler or controller that would help illustrate this?

And is there any reason if we're running CF9 why we shouldn't use the local scope in these situations?

TIA!

Sep 30, 2010 10:35:10 UTC

by Luis Majano

@Allen,

In cf9 you don't have to var scope if you use the local scope as that puts the variables in the local function scope. To me that is a matter of preference, like what color you like? They both achieve the same results.

Some example handler code of NOT var scoping:

function doThis(event){

rc = event.getCollection();

rc.data = service.getData();

}

Recent Entries

Your API Returns 200. Did the Business Transaction Actually Work?

Your API Returns 200. Did the Business Transaction Actually Work?

The customer submits an order. The portal shows a confirmation. The API returns 200 OK, and the release checks pass.

The next morning, operations asks why the order never appeared in the approval queue. Support has a ticket. A developer has to trace the order through the database and figure out whether someone can safely submit it again.

For teams maintaining a ColdFusion or Lucee application, this is a frustrating kind of release failure: the team ...

Maria Jose Herrera
Maria Jose Herrera
November 11, 2026
BoxLang AI 3.7: Profiles, Embeddings Defaults and MCP Rate Limiting

BoxLang AI 3.7: Profiles, Embeddings Defaults and MCP Rate Limiting

Ortus Solutions announces the release of BoxLang AI 3.7. Name a provider, model, params and API key once, then pick it by name for a call, an agent, or a single agent run. Embeddings get their own defaults, MCP servers you build get rate limiting and trusted proxies, and a handful of important fixes land along the way.

Luis Majano
Luis Majano
November 05, 2026
BoxLang  1.19.0: See Everything Your Code Does

BoxLang 1.19.0: See Everything Your Code Does

Ortus Solutions today announces the release of BoxLang 1.19.0, the software productivity platform for building, modernizing and running applications, with developers and AI agents working together. This release is about observability: built-in code coverage and execution profiling, the missing post-invocation events for BIFs, and new query and transaction events, and it pairs with the new BxLens beta, the debug bar and ops console that exposes hotspots and bytecode profilers. It also adds your own global settings in boxlang.json, static method interception, raw binary HTTP streaming and a lot of hardening across JDBC, Java interop and CFML compatibility.

Luis Majano
Luis Majano
November 05, 2026